Network Ports Requirements
The tables below describe the Kubernetes network requirements for UCT Container to work efficiently.
|
Universal Cloud Tap - Container deployed inside Kubernetes worker node |
||||
|
Direction |
Protocol |
Port |
Destination CIDR |
Purpose |
|
Outbound |
TCP |
42042 |
Any IP address |
Allows UCT-C to send statistical information to UCT-C Controller. |
|
Outbound |
UDP |
VXLAN (default 4789) |
Any IP address |
Allows UCT-C to tunnel traffic to the GigaVUE V Series Node or other destination. |
|
UCT-C Controller deployed inside Kubernetes worker node |
||||
|
Direction |
Protocol |
Port |
Source CIDR |
Purpose |
|
Inbound |
TCP |
8443 (configurable) |
GigaVUE-FM IP |
Allows GigaVUE‑FM to communicate with UCT-C Controller. |
|
Inbound |
TCP |
42042 |
Any IP address |
Allows UCT-C Tap to communication with Controller. |
|
Direction |
Protocol |
Port |
Destination CIDR |
Purpose |
|
Outbound |
TCP |
5671 |
Any IP address |
Allows UCT-C Controller to send statistics to GigaVUE‑FM. |
|
Outbound |
TCP |
443 |
GigaVUE-FM IP |
Allows UCT-C Controller to communicate with GigaVUE‑FM. |
The following table describes the ports that you need to open on GigaVUE‑FM:
|
Direction |
Port |
Purpose |
|
Inbound |
443 |
GigaVUE‑FM REST service port. |
|
Outbound |
8443 |
Allows GigaVUE-FM to communicate with UCT-C Controller. |
| Inbound | 5671 | Allows UCT-C to send statistics to GigaVUE-FM through Rabbit-MQ port. |
